###############################################################################
# #
# RCBco-30.zip: Carrier Operation Package for Military Jets #
# FSX ONLY #
# #
# By Rob Barendregt Release 3.0 25 feb. 2007 #
# #
########################################################################
WARNING: THIS IS NOT A "DOWNLOAD & FLY" PACKAGE. SO PLEASE TAKE YOUR TIME TO
******** READ THE DOCUMENTATION PROPERLY BEFORE YOU INSTALL & USE IT.
With that said: .... :-)
This archive contains a set of gauges, effects and sounds which you can add to
your existing military jets in FSX, and enables you to perform catapult takeoff's
and arrested landings on aircraft carriers (static AND moving).
Unfortunately adding gauges and effects to existing aircraft is a rather
cumbersome manual process, which is almost impossible to automate due to
the variety of aircraft, versions, updates, existing personal additions, etc.
For this reason I didn't included ready-made panel.cfg and aircraft.cfg
files. Besides, you might learn something from this manual process :-)
So installing this package REQUIRES some basic knowledge of handling files
and folders in Windows, and the ability to edit existing .cfg and .ini files
with a simple text editor like Notepad.
And for safety:
**** !! ALWAYS BACKUP A FILE BEFORE YOU EDIT IT !! ****
Lastly, special credits go to Doug Dawson; without his gauges that enable:
- Playing sounds from an XML gauge.
- Reading configuration data in an XML gauge, a.o. arrester&launch zone data.
- Controlling the aircraft speed during arrests and lauches.
this package would not exist !
0. Contents
===========
1. Overview
2. Installation.
2.1. Installing the files.
2.2. Adapting the panel.cfg file.
2.3. Adapting the aircraft.cfg file.
3. Detailed functionality and operation.
3.1 The COP3 Control Panel.
3.2. Carrier catapult launching: the catapult gauge.
3.3. Carrier landings: the arrester gauge.
3.4. Carrier approaches: the IFLOLS.
3.5. Breaking the sound barrier: the SonicBoom effects.
3.6. Using the test area for practicing.
4. Copyrights, Disclaimer and Credits.
5. Closure
Appendix-1: If you were using COP V2.0 for FS9 ....
Appendix-2: Requirements on the FSX environment you use ....
Appendix-3: How to add/modify launch & arrest zones ....
Appendix-4: How to adapt configuration defaults to your aircraft ....
Appendix-5: If the sounds (sonic boom, arrest/lauch) are too loud ...
1. Overview
===========
This package contains some features that you can add to your existing tailhook-
equipped aircraft and will work in any scenery / mission.
These features are:
- A Catapult gauge, allowing you perform a catapult-aided launches from defined
zones on a carrier. Includes a launch sound.
- An Arrester gauge, allowing you to land in a defined zone on a carrier deck,
by means of a tailhook "catching" the carrier's arresting cables. Includes
a catch sound and cable-rewind sound.
- A IFLOLS gauge, enabling you to perform proper carrier approaches.
- A SonicBoom gauge and effect (visible and audible), when your aircraft goes
through the sound barrier at MACH-1.
- A PositionDisplay gauge, that lets you define your own defined zones.
- A small, permanently visible Control Panel, that lets you open/close Windows
(like the IFLOLS) and change some package options.
Apart from "static" carriers, this version also support lauches and arrests on
the FSX "moving" carriers. However, with the limitation that zones are NOT
supported in this version.
Launches and arrests are made possible by (dynamically) enabling a "global"
zone, that allows launches and arrests on any spot in the FS world.
Unlike other programs, the included gauges are purely aircraft-bound; i.e. they
are defined in the panel and does not require startup of an external program.
These gauges require installation of Peter Dowson's FSUPIC interface module
(either a registered or unregistered version). This module is used to command
the acceleration / deceleration needed for takeoff / arresting.
See also Appendix-2.
If you want to know more about the operation and procedures on carriers, have
a look at the following website:
http://science.howstuffworks.com/aircraft-carrier.htm
2. Installation.
================
TIP: Use the Windows' Copy&Paste facility to avoid typing errors in copying text.
2.1. Installing the files.
==========================
Extract all files to your main FSX folder, using the "Use folder names" option.
This will place each file in it's correct location.
See also the pathnames in this zip file in case you copy manually.
DO NOT change the prescribed locations of the files !!
2.2. Adapting the panel.cfg file.
=================================
!! In the definitions below, replace the string "**" by the next free gauge number.!!
- Under [Window Titles], add:
Window17=COP Control Panel
Window18=IFLOLS
Window19=PositionDisplay
- Under [VCockpit01] (or, if no VC present, [Window00]), add:
//---------- COP3 Control Panel ------------
[Window17]
size_mm=52,12
visible=0
window_size= 0.045,0.015
window_pos= 0.55,0.02
background_color=16,16,16
ident=10080 //DO NOT CHANGE THIS VALUE
nomenu=1
gauge00=COP3!ControlPanel, 0,0,52,12
gauge01=COP3/CarrierZones!dsd_carrier_zones,0,0
gauge02=COP3/Config!config, 0,0,,, ./gauges/COP3/Config.ini
gauge03=COP3/Sound!dsd_xml_sound3, 0,0,,, ./gauges/COP3/Sound.ini
gauge04=COP3!Arrester, 0,0
gauge05=COP3!Catapult, 0,0
gauge06=COP3/SpeedControl!xml2ipc, 0,0
gauge07=COP3!SonicBoomControl, 0,0
//------------- COP3 IFOLS ----------------------
[Window18]
size_mm=477,215
visible=0
window_size= 0.2,0.12
window_pos= 0.0,0.1
background_color=0,0,0
ident=10081 //DO NOT CHANGE THIS VALUE
nomenu=1
gauge00=COP3!IFLOLS, 0,0,477,215
//------------- COP3 Position Display ------------
[Window19]
size_mm=180,110
visible=0
position=2
ident=10082 //DO NOT CHANGE THIS VALUE
nomenu=1
background_color=16,16,16
gauge00=COP3!PositionDisplay,5,5,170,100
*******************
Notes:
1. By varying the values of window_size and window_pos (values 0.0 - 1.0) in a
Window definition, you can change the default size and position of that Window.
2. In case you panel.cfg already contains Window17,18,19, please use other
numbers. The numbers are not critical.
3. If you are using a Panel Editor to add these gauges to your aircraft, make sure
that it doesn't remove the 5th parameter in the gauge definitions.
Like in: gauge02=COP3/Config!config, 0,0,,, ./gauges/COP3/Config.ini
4. If your \gauges folder allready contains a file dsd_catapult_zones.ini or
dsd_arrester_zones.ini, make sure you back it up first. The include versions
only contains very limited zone definitions.
2.3. Adapting the aircraft.cfg file.
====================================
!! In the definitions below, replace the string "**" by the next free light number.!!
- (Only if you aircraft is capable of Mach-1 airspeeds)
Under [LIGHTS], add:
light.**= 10, -10.0, 0.0, 0.0, fx_RCB_machenvlop,1 // SonicBoom visual effect
NOTES:
- The light.** numbers range from 0 - 18. If no free number exists, you have
to delete another effect.
- Check that the file has a [Tailhook] section. See also Appendix-2.
3. Detailed functionality and operation
=======================================
3.1 The COP3 Control Panel.
==============================
This is a small gauge in a permanently visible window, by default placed on
the top-center of the screen. It has 4 tooltipped clickspots, that do the
following (from left to right):
1. IFLOLS control.
Left-Clicking this spot, toggles the IFLOLS window open/closed.
When the spot lights up Green, the aircraft is in the visibility range of
the IFLOLS.
2. Zone Control.
Left-Clicking this spot, toggles the PositionDisplay window open/closed.
- When the spot lights up Green, the aircraft is within a launch or arrest
area (defined or global)
- When the spot flashes Green, the catapult is armed for launch.
Right-Clicking this spot, toggles the GlobalZone On/Off.
3. Tailhook Control.
Clicking this spot, toggles the tailhook off/on.
- When in the air:
- Flashing Green: tailhook is lowering.
- Steady Green: tailhook is fully lowered.
- When on the ground:
- Flashing Green: tailhook is lowering.
If it remains flashing after a few seconds: tailhook is too short or to long.
- Steady Green: tail on the ground, and has correct lenght.
4. Window location.
Drag on this spot to move the window.
By default, opening the IFLOLS and PositionDisplay windows can only be done via
this Control Panel, not via the FSX menu; with the advantage however, that these
windows remain forced open whatever view (camea) you select.
3.2. Carrier catapult launching: the catapult gauge
===================================================
This invisible gauge has an automatic Arm and Release function (see below).
On a real carrier, the catapult is preset to accelerate the aircraft to reach
launchspeed over the shuttle travel distance. This means that the catapult force
(steam pressure) is adjusted for aircraft weight, required launchspeed, current
wind and current carrier speed.
Used defaults:
- Launchspeed: 160 Knots TAS.
- Catapult distance: 300 ft.
But these values can be changed in the config.ini file. See Appendix-4.
In a simple case (Launchspeed= 160 Knots TAS, carrier speed at lauch= 0, no wind),
this means that the aircraft is launched in appr. 2 seconds.
A normal operating procedure is:
- Line up the aircraft at the catapult, just in front of the Jet Blast Screen
(if your carrier scenery has one) untill the Zone Control light on the Control
Panel turns Green.
This means that you are now in the defined launch zone.
- Set 3/4 - Full flaps, and set the ParkingBrakes.
By setting the ParkingBrakes you Arm the catapult (i.e. the aircraft nosewheel
is coupled to the catapult shuttle). The Zone Control light now flashes.
- Open the throttles fully.
When the engines are spooled up, the Parking Brakes are automatically released
and the aircraft is launched.
"Spooled up" means: the LaunchN1, as defined in the config.ini (see Appendix-4)
is exceeded.
Note: if you have activated the Global zone in the Control Panel, this means that
you can launch from any point in the world. So beware that you don't spool
up the engines on just any point (with ParkingBrakes set), or your aircraft
will be launched :-)
3.3. Carrier landings: the arrester gauge
=========================================
****** IMPORTANT ******
For this gauge to operate properly, your aircraft MUST have a proper "functional"
tailhook, defined in the aircraft.cfg. See Appendix-2.
On a real carrier, the arrester wires (through damping cylinders) are preset to stop
all aircraft at roughly the same point; hence the stopping force applied depends on
estimated aircraft weight, carrier speed and expected touchdown speed.
Used defaults:
- Stopping distance: 280 ft.
But this value can be changed in the config.ini file. See Appendix-4.
In a simple case (Touchdown speed= 160 Knots, deckspeed= 0), this means that the
aircraft is arrested in appr. 2 seconds.
A normal operating procedure is:
- During final approach, line up the aircraft with gear and flaps down, and proper
heading, landing speed and descent rate.
The IFOLS will be of great help here.
- Lower the tailhook, either via a keyboard key / joystick button assigned to the
FSX event for "Tailhook (up/down)" (in Options-Settings-Controls, tab Buttons/Keys)
or by clicking the Tailhook Control spot on the Control Panel.
- When the tailhook touches the deck within a defined Arrester zone and with the
correct heading, the aircraft is quickly decelerated to a full stop (the catch
sound is played), after which it is pulled back a bit.
About 4 seconds later, the tailhook is automatically raised, and the cable
rewind sound is audible.
- To enhance realism: in FSX menu Aircraft - Realism Settings, set "Detect crashes"
to On. If you touchdown too fast or too hard, the aircraft will crash.
Note: if you have activated the Global zone in the Control Panel, this means that
you will be arrested at any point in the world, if you land with an extended
tailhook. Use this for landings on moving carriers. See Appendix-2.
3.4. Carrier approaches: the IFLOLS.
====================================
This IFLOLS (Improved Fresnel Lens Optical Landing System) gauge emulates an IFLOLS
found on real carriers, and allows you to "fly the meatball" for arrested landings.
Of course, this is a simplified version of the real thing, with the most obvious
differences being:
- This IFLOLS is fixed in your aircraft panel, and not on the carrier scenery.
- It's based on the presence of a full ILS system (with Localiser, Glideslope and DME)
on the carrier. The ILS frequency must be dialled into the NAV1 radio.
For most commonly used ILS's, the glideslope beam angle and beam width are about the same
as the vertical angle of visibility of the "meatball" on a real IFLOLS (resp. 3 and 1.75
degrees). However, the ILS Localiser beam width usually is 5-10 degrees, while the
lateral visibility angle for a real IFLOS is 20 degrees.
In this gauge, I deliberately "streched" up the functionality of the IFLOLS, to give
more info on approach:
- Visibility distance is default 7 nMiles (IRL: 1.5 nmile)
- Waveoff distance is at default 0.5 nMiles (IRL: Variable)
- DatumLights are flashing when outside the horizontal beam (IRL: not)
The gauge is activated via IFLOLS clickspot on the Control Panel, and its lighting works
as follows (see also included IFLOLS.jpg picture).
- Any light only works, if:
- ILS Localiser and Glideslope needles are detected.
- ILS DME detected and aircraft is within the defined visibility range.
- Green CutLights, if:
- Aircraft within landing speed limits (default: 120 to 200 knots), and
- Gear and tailhook down.
- Green DatumLights, if:
- Within the Localiser beam.
- Flashing Left: when left of the Localiser beam.
- Flashing Right: when right of the Localiser beam.
- MeatballLight, if:
- Within the glideslope beam.
- RED: lower 2 lights of the range.
- YELLOW: upper 10 lights of the range.
When exactly "on glideslope", the MeatballLight is centered between the DatumLights.
- Flashing Red WaveoffLights, if at waveoff detection distance:
- Outside the center of the glideslope beam (outside middle 8 lights)
- Outside the localiser beam.
- Aircraft not within landing speed limits.
- Gear or tailhook not down.
The WaveoffLights remain flashing untill one the general light conditions become
false.
The "defaults" mentioned above are read from the config.ini file. See Appendix-4.
3.5. Breaking the sound barrier: the SonicBoom effect
=====================================================
Go into Spotplane view, let your aircraft accellerate to MACH-1, and observe
the "cloud" being formed and pushed forward by the aircraft; when the aircraft
reaches MACH-1, it punches through the cloud and the Boom sound is played.
Needless to say this effect is only usefull for supersonic aircraft :-)
3.6. Using the test area for practicing
=======================================
To fully test your installation and/or practice launches and arrested landings,
I have included a test scenery at TFFG airport (St.Maarten).
Nothing fancy, just textures on the existing runway plus an ILS.
The catapult and arrester zones for this test are already pre-defined in the
included .ini files.
For a catapult lauch: Position the nosewheel of your aircraft exactly on the
black spot in the launch area (the shuttle of the catapult), with heading 121.
For an arrested landing:
- Set your NAV1 radio to 117.90 (the ILS freq. of the arrester zone).
- Open the IFLOLS window.
- Approach the arrester zone with heading 121, following the "meatball".
Should the ILS not work, or the runway "launch" and "arrester" textures not be
visible: check that:
- The standard FSX "ADDON SCENERY" is not disabled in your scenery.
- You don't use another addon on TFFG; my textures are based on the default
TFFG FSX runway scenery.
NOTE: At short distance, ignore the runway VASI lights from the default FSX
scenery, because they reference to a different landing spot.
(they will indicate that you are too low).
4. Copyrights, Disclaimer and Credits
=====================================
This package is freeware (NOT: public domain), and is available for your
personal use.
Without my explicite permission, it may NOT be sold, re-distributed and/or
uploaded to another website or bulletin board in ANY shape or form.
If you want to bundle this package with your (freeware) aircraft, you may ONLY
do so AFTER my explicite permission, and inclusion of the documentation.
And obviously, installing & using this package is at your own risk.
However, if you execute the Installation instructions properly, this package
should NOT crash you PC or FSX, nor should it have a substantial impact on
performance.
Credit goes to:
- Doug Dawson, as explained in the introduction..
- Nick Needham, for his spectacular SonicBoom visual effect.
- Aaron R. Swindle. The included catapult and cablecatch sounds are re-mixed
and adapted versions of original recordings made by Aaron.
- Pete Dowson, for making and maintaining FSUIPC.
5. Closure
==========
I hope you will enjoy using this package, as I did creating it.
And I'm always open to questions, or suggestions for improvement (no guarantee
that I will make them though).
But PLEASE PLEASE, before asking me questions or report "bugs", make sure that
the answer can't be found in this README file; I have spent considerable time
in making this as clear and supportive as I can, just to avoid wasting both
YOUR time and MINE with trivial questions and "issues" :-)
Enjoy ......
Rob Barendregt, The Netherlands
Email: rc.barendregt@planet.nl
Appendix-1: If you were using COP V2.0 for FS9 ....
===================================================
The main differences with V2.0:
- Slightly improved, now configurable launch&arrest algoritmes.
- Arrests now only works based on tailhook compression, NOT on "aircraft landed".
- The .ini files that contain the zone definitions, now can contain 250 entries each.
- Meatball HUD is replaced by a more realistic IFLOLS.
The IFLOLS requires the presence of an ILS though.
- Works for moving carriers as well (with a "global" zone only).
- For launches: implicite Arming (i.e. ParkingBrakes are set in a launch zone)
- Easier to install:
- Using seperate windows.
- Launch and arrester gauges are invisible, and need no placing the main panel.
- Window handling / configuration via a permanently visible, small Control Panel.
Appendix-2: Requirements on the FSX environment you use ....
============================================================
1. FSUIPC installation / gauge trusting.
----------------------------------------
This solution also requires prior installation of Peter Dowson's FSUIPC:
FSUIPC.dll (V4.0.7.0 or later, registered or unregistered).
You can download and install the lastest version of FSUIPC at:
http://www.schiratti.com/dowson.html
When loading the aircraft for the first time, you might be asked to "trust" Peter
Dowson's FSUIPC and Doug Dawson's modules; if you "trust" them, and also say "Yes"
when asked to trust all modules from Peter and Doug, you will never asked again.
If lauches/arrests do not appear to work properly: there may be several causes.
The new SimConnect interface in FSX sometimes doesn't always work properly (known bugs)
Moreover, there are some known problems with SimConnect/FSUIPC w.r.t virusscanners
and firewalls; SimConnect communicates via TCP/IP with FSX !
If you experiance these problems, check the FSUIPC website/forum for solutions;
there are several threads about this subject.
To check if SimConnect/FSUIPC is working properly: check if your Menu bar in FSX
contains an item "Addons", with "FSUIPC" in it.
2. Tailhook definition.
-----------------------
In principle, this package can be added to any aircraft equipped with a tailhook
that is operated by the standard FS ToggleTailhook command. However, this requires
that the tailhook is properly defined; iow. when the aircraft is in the air, the
tailhook should stick out below the landing gear.
If it isn't, arrests may still work depending how you touchdown.
As said, the arrester gauge works based on the fact that the tailhook is compressed
when it touches the deck/ground in the defined arrest zone; which is IMO most realistic
criterium; this unlike some other packages, that arrests the aircraft either when the
wheels touch the deck, and/or when the aircraft is below a certain altitude with the
arrest zone.
However, to prevent arrests not working because of a wrong tailhook definition (too
short, so it won't be compressed upon landing), I also added the "aircraft on ground"
criterium for arresting (if tailhook extended and within the arrest zone, of course).
The difference between the two arrest criteria is obvious:
- With "tailhook compression" (i.e. the hook catches the wire), the aircraft is
arrested while the main gearwheels do not touch the deck yet. Like in real life.
- With "aircraft on ground", the aircraft is arrested when the main gearwheels touch
the deck. However, this isn't fool-proof as well :-) : if you land with too high
airspeed or too high descent rate, the aircraft might "bounch" so the arrester gauge
cannot detect the touchdown.
You can verify correct Tailhook operation in aircraft as follows:
- Set your aircaft on the deck/runway and give it a very low weight (reduce fuel to
10% and remove all payload via menu Aircraft - Fuel&Payload).
- Lower the Tailhook by clicking the Tailhook spot on the Control Panel.
- After a second or so, the light should be steady green. See also the tooltip.
- If you open the PositionDisplay window (by left-clicking the Zone Control spot),
you can see the actual tailhook extension percentage.
This should be around 60-70 % for best operation..( <40%: too long, >80: too short)
If the Tailhook length is NOT correct:
- Open the aircraft.cfg of the aircraft, and find the section (just an example):
[TailHook]
tailhook_length=6.6
tailhook_position = -15.0, 0.0, -1.0 //-1.0 = lateral position of the tailhook
cable_force_adjust = 1.0
- Change the 3rd parameter of the _position= a bit, and try again.
Note that, after saving the aircraft.cfg and reloading the aircraft again, the fuel
level isn't changed, but FSX assigns the full payload again (as defined in the aircraft.cfg).
In this example:
- Changing -1.0 in -0.5 raises the Tailhook, so the % extension on the ground will increase.
- Changing -1.0 in -1.5 lowers the Tailhook, so the % extension on the ground will decrease.
Proper values for some aircraft I have:
- For the IRIS F14A:
[TailHook]
tailhook_length=6.6
tailhook_position = -15.0, 0.0, -2.1
cable_force_adjust = 1.0
- For Dino Cataneo's F14D: (the basic model for many freeware F14 uploads):
[TailHook]
tailhook_length=4.0
tailhook_position=-21.0, 0.0, -0.6
cable_force_adjust=1.0
- For the IRIS Phantom FG1
[Tailhook]
tailhook_length=3.0
tailhook_position=-17.5,0.0,-4.1
cable_force_adjust=1.0
3. Aircraft and aircraft carriers.
----------------------------------
There are several carrier packages from the FS9 era that work in FSX.
E.g. carr2006.zip (a.o. on SurClaro). Note that the zone definitions
may be slightly different in FSX, a.o. due to new MagVar definitions.
Be warned though: with some I tested, aircraft crashes (if you have crash-detection
On) when you are near the carrier. This has nothing to do with my package !
Solution: set crash-detection Off.
If you want to try your skills on a moving carrier:
- In FSX, select Mission "Tutorial 11: Helocopter Maneuvers 1" and check the box
"Enable changes in selected mission" and "Show saved missions"
- Select your modified aircraft instead of the helicopter.
- Select "Global zone" by right-clicking the ZoneControl spot on the COP3 Control
Panel. The green light should be On now.
- Approach the carrier from behind, and land .....
- But I strongly suggest you practice arrested landings on static carriers first :-)
Especially since the IFLOLS is of no use, since a "moving ILS" still has to be
invented..
As far as FSX aircraft is concerned: at this moment there aren't many FSX-compliant
arrest-capable aircraft (freeware or payware) around yet. However, a lot of the FS9
aircraft (e.g. F14/F18's) can be installed in FSX, if you accept the usual incompatible
"FS98-style" gauges. But please, don't ask me to support you installing these aircraft
in FSX; I simply don't have enough spare time.
On the other hand: my package will work with any FSX aircraft (even a 747 ..LOL ),
provided you equip this aircraft with a "functional" tailhook by adding a [tailhook]
section as described above. Although the tailhook won't be visible of course !!.
Appendix-3: How to add/modify launch & arrest zones ....
========================================================
The area's in which a catapult lauch or cable arrest is possible, are defined in
files dsd_catapult_zones.ini resp. dsd_arrester_zones.ini in the \Gauges folder.
So you can easily add your own zones by editing these .ini files with Notepad.
The included .ini files only contain the zones I use myself for now:
- The CVN-72, off Miramar MCAS (4 catapults). From the Carr2006.zip package.
- My test area on TFFG airport.
Each zone must have a unique zone number (00 - 249), so you can define 250
zones in each .ini file.
In the .ini files, you'll see the lines
[Config]
CourseTolerance=5 (max: 180)
This means that the aircraft heading must be within -5 and +5 degrees of the
zone heading (as defined by RunwayHeadingInDegreesMag). If not, the Catapult
is not armed resp. the aircraft is not arrested.
You can define new zones accurately (or check existing zones), by using the
PositionDisplay gauge.
- Start FSX
- Create/Select a flight that positions the aircraft in a zone you want to define.
- Activate SlewMode.
- Set FS into TopDown view via menu Views - ViewMode - TopDown view.
- Zoom in/out as appropriate, using the +/- keys.
- Left-click on the Zone Control spot on the COP3 Control Panel
- With the aircraft in the exact zone heading, slew to the 4 corners of the zone
you want to define, and make a note of the coordinates.
- Read the Altitude and Zone heading, and copy this info as well.
- Exit FSX.
- Edit the .ini file(s) with the obtained data and save them.
- Start FSX again and check the new zone.
The PositionDisplay gauge turns:
- GREEN: If aircraft within a defined zone.
- RED: if not.
And if this is too much work: just use the "global" zone for arrests and launches.
NOTE: the launch / arrest zone definitions you used in FS9 may be slightly different
in FSX, a.o. due to new MagVar definitions.
Appendix-4: How to adapt configuration defaults to your aircraft ....
=====================================================================
File Config.ini is read by gauge Config.gau, and sets various startup variables.
When the gauge is loaded, the internal variables are initialised to the values
in the [Floats] section; when the gauge is unloaded (when reloading an aircraft
or flight, or exiting FSX) the current values are saved for next session.
SO: if you exit a flight with e.g. Global Zone ON, the next flight flight with
this config.ini starts up again with Global Zone ON. !!
The [Lvars] section contains the L: variables definition, the [Floats] section
contains the related values.
So e.g. Lvar_03 has the value defined by Value_03.
To change the value of a parameter manually, open Config.ini with Notepad and
simply replace the value of Value_**= .
WARNING:
- In Config.ini ONLY edit the values of Value_** , nothing else !!!
- DONOT attempt to change Config.ini while FSX is running.
The changes you make will be lost !!!
[Floats]
Value_00=0. This parameter defines whether you are using a world-wide, global zone
for arrests & launches, or the limited zones as defined in the files
dsd_arrester_zones.ini and dsd_catapult_zones. ini.
When OFF, launches and arrests are only possible within the defined zones.
When ON, lauches and arrests are possible anywhere.
- Launch: When N1 exceeds the defined CatapultLaunchN1 while ParkingBrakes are set.
- Arrest: When the aircraft touches down with an extended tailhook.
0: Global Zone is OFF.
1: Global Zone is ON.
Value_01=7. The distance (in nMiles) from the ILS, from which the IFLOLS will work.
Value_02=0.5 The distance (in nMiles) from the ILS, at which an approach check is done.
Value_03=70. The % N1, at which (when exceeded) the aircraft will be lauched when the catapult
is Armed; ie. within a launch zone with ParkingBrakes set.
TIP: Do not set this value too high, otherwise the brakes won't hold the aircraft
at it's place before this LaunchN1 is exceeded.
Value_04=160. The required airspeed (in knots TAS) at the end of the catapult.
Value_05=300. The length of the catapult (in feet).
Value_06=280. The distance over which the aircraft is stopped after an arrest (in feet)
Value_07=120. The Min. landingspeed (in knots); if below this airspeed, you will be waved off.
Value_08=200. The Max. landingspeed (in knots); if above this airspeed, you will be waved off.
Note that the parameters are related to the gauge, NOT to a saved flight !
This also means that you can have seperate Config.ini files for different aircraft.
To to this:
- Make a copy of the Config.ini file, and name it e.g. MyConfig.ini
- In the panel.cfg, section [Window17], change the path for gauge02 to:
gauge02=COP3/Config!config, 0,0,,, ./gauges/COP3/MyConfig.ini
Appendix-5: If the sounds (sonic boom, arrest/lauch/cable-rewind) are too loud ...
=================================================================================
The volume of the sounds played in this package are not influenced by the FSX sound sliders.
If you find any of the played sounds too loud, you can change the volume yourself
in the sound.ini file; individually per sound.
Just open the sound.ini file with Notepad, find the right .wav file, and edit the
volume number in that line:
- 100 is max. (default) volume.
- 70 is the min. volume (makes the sound almost inaudible)
Or, set the FSX sound sliders higher (and your speaker volume lower).
If you find the played sounds not loud enough, the only way is to set the FSX sound
sliders lower (and your speaker volume higher) for better balance with the FSX sounds.
************************************************* END OF DOCUMENT ***********************************
